home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Libris Britannia 4
/
science library(b).zip
/
science library(b)
/
INFO
/
PCCDEMO.ZIP
/
COMP1.EXE
/
ABV640K.PRS
< prev
next >
Wrap
Text File
|
1993-12-20
|
5KB
|
76 lines
╧╧╧╧╧╧╧╧╧╧╧╧╧╧╧╧╧╧╧ ÅæÄåæÇîîêìå: BEYOND 640K ╧╧╧╧╧╧╧╧╧╧╧╧╧╧╧ ╬╠╬╠╧╧╬╠╬╠╬╠╡
│ ¢. ö≥Σ ùîÆ ε± äîÆ ∞Σ∞ε±√. XMS is
▄ ▄ │ preferable in most cases, but
█▄▄ ▄▄▄ ▄ ▄ ▄▄▄ ▄▄▄ ▄▄█ │ some machines won't provide it.
█ █ █▄█ █ █ █ █ █ █ █ █ │ There are some libraries
█▄█ █▄▄ █▄█ █▄█ █ █ █▄█ │ available at Simtel to access XMS
▄▄█ │ or EMS. The disadvantage is that
▄ │ you don't allocate the memory as
▄▄▄ ▄ ▄▄▄ █ ▄ │ you would with malloc() (or `new'
█▄▄ █ ▄ █ █ █▄▀ │ in C++). I believe it also
█▄█ █▄█ █▄█ █ █ ▄ ▄ ▄ │ requires that you lock this
▀ │ memory when in use. This means
│ your code is not easily ported to
ü√ ëα∞≥τΦπ Çσ≥τα± αφπ │ other (and future) operating
â⌠φΓαφ î⌠±πεΓτ │ systems and that your code is
│ more convoluted than it would be
│ under a "real" os. The advantage
çΣ±Σ α±Σ ≥ε∞Σ ΦπΣα≥, εφ │ is that the library works with
∩±εµ±α∞∞Φφµ ÷Φ≤τ αΓΓΣ≥≥ ≤ε ∞Σ∞ε±√ │ compilers since Turbo C 2.0 (I
αßε⌡Σ á₧Üè. │ think) and that your program will
│ easily run on even 286s.
£. Å±εµ±α∞ ⌠φπΣ± îÆ ûΦφπε÷≥. MS │ course, run the program from
Windows functions as a 16-bit DOS │ Windows.
Extender (see #3). Borland/Turbo │
C++ 3.x includes EasyWin [and │ ¥. ö≥Σ α ¢á-ßΦ≤ ε± ¥£-ßΦ≤ âÄÆ
Microsoft C/C++ 7.0 has QuickWin │ ä≈≤ΣφπΣ±. This is definitely the
--ed.] which is a library that │ best solution from the program-
automatically lets you compile │ mer's standpoint. You just
your current code using C/C++ │ allocate as much memory as you
standard input or <conio.h> into │ need using malloc() or 'new'. A
a MS Windows program so your code │ 16-bit Extender still has 16-bit
can immediately allocate many MBs │ ints and restricts arrays to 64K,
of memory (Windows enhanced mode │ but a 32-bit Extender has 32-bits
even does virtual memory). The │ ints (which makes porting a lot
disadvantage is that like any 16- │ of UNIX code easier) so there are
bit Extender a single malloc() is │ no 64K limits. A 32-bit Extender
restricted to 64K (unless you │ requires a 32-bit compiler and
want to mess with huge pointers │ the program will not run on 286s.
in Windows). Also, EasyWin's │ Some Extenders also do virtual
screen output is significantly │ memory. Using an Extender
slower than a DOS character-mode │ doesn't require source code
program's and you must, of │ changes and unlike option #1 your
code is portable and not obsolete │
in a few months. ÿε⌠± ε∩≤Φεφ≥ σε± │ - Get a 32-bit compiler or
≤τΦ≥ ≥εδ⌠≤Φεφ α±Σ: │ one that comes with a DOS
│ Extender. Zortech comes with 16-
- Buy PharLap's 16-bit │ bit and a 32-bit Extenders (no
Extender that works with BC++ │ debugger for 32-bit programs, but
3.0+ and MSC (just requires a │ Flashtek sells one). Watcom also
relink). Note, the BC++ 3.1 │ makes a C 32-bit compiler. [If
upgrade came with PharLap "lite". │ anyone else has products or plans
Pharlap's 32-bit Extender works │ to announce, please let us know.]
with 32-bit compilers. │
│ - Buy Borland Pascal 7.0.
- Get the GNU (free, │ It includes a 16 bit royalty-free
copylefted) gcc 2.x compiler │ DOS extender using the same
which DJ Delorie ported from UNIX │ interface as MS Windows. It
and which uses his 32-bit │ functions under a DPMI server
Extender. It supports C and C++, │ like Windows or QDPMI from
but the Extender is VCPI which │ Quarterdeck, and also provides
means neither the compiler nor │ its own server which you can
programs it produces will run in │ distribute with your programs.
a DOS session under Windows. │
4. This option doesn't really │
count since it's not a solution │
in DOS, but √ε⌠ Γε⌠δπ ≥÷Φ≤Γτ ≤ε α │
σ⌠δδ ¥£-ßΦ≤ ε∩Σ±α≤Φφµ ≥√≥≤Σ∞ │
like OS/2 2.0 or UNIX (or NT when │
it comes out). I believe Win32 │
will allow you to write 32-bit │
Windows programs ñ │